Post-Installation Adjustments
During the initialization phase, the application is installed with default settings and sample content. Often, these default settings need to be changed in production environments.
Authentication Provider
Note: Open LDAP, Azure Active Directory, SAML, and OpenID authentication are not available in the Community Edition.
Default Authentication Provider
By default, Pyramid is installed with internal Database authentication, which requires little configuration. An initial user is created using the user ID and password supplied during the installation and assigned Enterprise Admin rights. If you are going to use the internal database, you do not have to do anything more to be able to begin work. You can, however, change to a different Authentication Provider.
Changing Authentication Provider
Whenever you change your authentication provider, you must provide the settings that will be used in the authentication engine, together with an initial master user account from that provider. This user will become the first enterprise user in the new setup.
- In the Admin Console, click Security > Authentication.
- From the top-right of the page, click Change Provider.
The Authentication Provider page opens with the details of your current Authentication Provider displayed.
The Change Provider page opens. By default, the Provider that you already have is selected in the Providers list.
From this page you need to select the Authentication Provider that you would like to move to and supply access details, credentials for a master user, and, where applicable, domain details.
Supported Authentication Providers are: Database (the internal and default authentication provider), Active Directory, Azure Active Directory, Open LDAP, SAML, and OpenID.
- Click here for full information about changing provider
Authentication Method
Apart from changing the authenticating provider, admins can also select their authentication method in the authentication panel. By default, the authentication method is set to Forms.
- Click here for more information about Authentication Methods
The method chosen is NOT affected by the use of third-party web servers.
Authentication changes must be made from inside the application - not from third-party web servers.